Secure detection and correction of inefficient application configurations

ABSTRACT

Methods and systems for detecting and correcting inefficient application configurations are presented. In one embodiment, a method is provided that includes receiving an application and executing the application multiple times according to different configurations. While executing the application, execution metrics may be measured associated with the different configurations. A classifier model may be trained based on the execution metrics and the different configurations. In particular, the classifier model may be trained to identify preferred configurations of the application. The classifier model may be provided to a second computing environment and may be used to identify inefficient configurations for subsequent deployments of the application within the second computing environment. The inefficient configurations may be identified without transmitting configurations or applications from the second computing environment.

BACKGROUND

Applications may execute in computing environments, such as distributedcomputing environments. Applications that execute in such computingenvironments may support multiple configurations that adjust theoperation of the applications based on one or more factors. Certainconfigurations may operate better under certain types of conditions,while other configurations may operate better under different types ofconditions.

SUMMARY

The present disclosure presents new and innovative systems and methodsfor detecting and correcting inefficient application configurations. Inone embodiment, a method is provided that includes receiving anapplication for execution in a first computing environment. Theapplication may be executed a plurality of times according to aplurality of configurations and a plurality of execution metrics may bemeasured that are associated with the plurality of configurations. Aclassifier model may be trained to identify one or more preferredconfigurations for the application based on the plurality of executionmetrics and the plurality of configurations. The classifier model may beprovided to a second computing environment. The classifier model maythen be used to detect inefficient configurations for subsequentdeployments of the application within the second computing environment.In particular, the classifier model may detect inefficientconfigurations of the application without transmitting configurations orthe application from the second computing environment.

The features and advantages described herein are not all-inclusive and,in particular, many additional features and advantages will be apparentto one of ordinary skill in the art in view of the figures anddescription. Moreover, it should be noted that the language used in thespecification has been principally selected for readability andinstructional purposes, and not to limit the scope of the disclosedsubject matter.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A illustrates a computing environment for correcting applicationconfigurations according to an exemplary embodiment of the presentdisclosure.

FIG. 1B illustrates a testing environment for application validationaccording to an exemplary embodiment of the present disclosure.

FIG. 2 illustrates a configuration according to an exemplary embodimentof the present disclosure.

FIG. 3 illustrates an operation to correct an application configurationaccording to an exemplary embodiment of the present disclosure.

FIG. 4 illustrates a method for training and deploying a classifiermodel according to an exemplary embodiment of the present disclosure.

FIG. 5 illustrates a method for validating, deploying, and correctingthe configuration of applications according to an exemplary embodimentof the present disclosure.

FIG. 6 illustrates a system according to an exemplary embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

In certain instances, users may execute applications on computingenvironments (e.g., cloud computing environments) provided andconfigured by another entity (e.g., a cloud computing provider). Forexample, users may execute applications in a cloud computing environmentimplemented by a third party and configured and accessed according tothe Red Hat® OpenShift® and/or Kubernetes® protocols. Conditions withinsuch computing environments may vary, which may change theconfigurations required for applications to execute properly and/orefficiently. It may therefore be unduly burdensome for users toconfigure applications properly and to update configurations in responseto changes in the current conditions within the computing environments.Furthermore, applications that are incorrectly configured may utilizeexcessive computing resources within the computing environment and/ormay not properly execute to fulfill expected functions. For example, anapplication may be configured to execute with too many instances for itsworkload, and the additional instances may unnecessarily utilizecomputing resources (e.g., processing cores and/or memory capacity)within the computing environment (e.g., on a cluster or clustersexecuting the application). As another example, an application may bemigrated from one computing environment to a new computing environment(e.g., from a first set of clusters to a second set of clusters). Thenew computing environment may have different computing resources and maytherefore necessitate a different configuration.

Therefore, it may be necessary to identify when an application executingwithin a computing environment has been incorrectly configured. Onesolution to this problem is to train a machine learning model toidentify when the configuration of an application results in lower thanexpected execution metrics. For example, the machine learning model maybe trained in a testing environment configured to test and validatevarious application configurations before deploying applications. Then,within a computing environment executing a deployed application, themachine learning model may analyze the configuration of the applicationand/or execution metrics of the application to identify a correspondingconfiguration. Based on the corresponding configuration, expectedmetrics may be identified and the expected metrics may be compared tothe execution metrics of the application. The configuration of theapplication may then be updated if a difference is identified betweenthe execution metrics and the expected metrics (e.g., a differenceindicating that the execution metrics are worse than the expectedmetrics).

FIG. 1A illustrates a computing environment 100 for correctingapplication configurations according to an exemplary embodiment of thepresent disclosure. The computing environment 100 may be configured toexecute applications 114, 116, 118. In particular, the computingenvironment 100 includes processor(s) 142 and memory 144, which may beutilized to execute the applications 114, 116, 118. For example, one ormore cores of the processor(s) 142 and particular amounts of the memory144 may be allocated to each of the applications 114, 116, 118 forexecution. In certain implementations, the computing environment 100 isan exemplary implementation of all or part of a cloud computingenvironment (e.g., a cluster of a Kubernetes® cloud environment) orother distributed computing environment. For example, the computingenvironment 100 may be configured to execute applications on behalf ofentities different from an entity implementing the computing environment100. The applications 114, 116, 118 may execute to perform differentfunctions. For example, the application 114 may be executing as a datagrid providing access and/or storage of data to other users, includingusers external to the computing environment 100. As another example, theapplication 116 may be executing to provide data synchronization betweenmultiple computing clients. As a further example, the application 118may execute to provide a send/receive buffer (e.g., forsending/receiving data) for the applications 114, 116.

Each of the applications 114, 116, 118 may have an associatedconfiguration 108, 110, 112 and/or execution metrics 120, 122, 124. Theconfigurations 108, 110, 112 may be applied by an applicationprogramming interface (API) service 102. The API service 102 may beconfigured to interface with the applications 114, 116, 118 in order toensure that the applications 114, 116, 118 execute according to theconfigurations 108, 110, 112. Specifics regarding applicationconfigurations are discussed in greater detail below in connection withFIG. 2.

The execution metrics 120, 122, 124 may specify information regardingperformance of each of the applications 114, 116, 118. The executionmetrics 120, 122, 124 may be collected by a metrics service 104 of thecomputing environment 100. For example, the metrics service 104 may beconfigured to interface with the applications 114, 116, 118 and/orportions of the computing environment 100 (e.g., networkinginterfaces/services, resource utilization monitors) to determine theoperating conditions of the applications 114, 116, 118 and to store theoperating conditions (e.g., operating conditions over time) as executionmetrics 120, 122, 124. The execution metrics 120, 122, 124 may becollected on a regular basis, such as, e.g., every second, every 15seconds, every minute, every five minutes, every 10 minutes. Theexecution metrics 120, 122, 124 may provide average performance measuresover a period of time, such as a rolling period of time (e.g., the last10 seconds, the last minute, the last 10 minutes) or for a period oftime with a fixed starting point (e.g., since execution of theapplication 114, 116, 118 began). The execution metrics 120, 122, 124may differ depending on the type of application 114, 116, 118. Forexample, for an application 114 executing to provide a data grid, theexecution metrics 120 may specify a request throughput reflecting anaverage rate at which requests are received for the data grid, a requestlatency reflecting average response time to the received requests, andan average startup time for instances of the application 114. As anotherexample, for an application 116 providing data synchronization, theexecution metrics 122 may specify an amount of data transferred, timesat which data is transferred, and data transfer latency indicating anaverage time it takes for data updated on one computing client to beupdated on another computing client. As a further example, forapplications 118 executing to provide a send/receive buffer, theexecution metrics may include one or more of a request throughput,request latency, and average buffer utilization indicating an averageamount of buffer space utilized during execution. Additionally oralternatively, the execution metrics 120, 122, 124 may indicate measuresof resource utilization by the applications 114, 116, 118. For example,the execution metrics 120, 122, 124 may indicate an amount of processingpower (e.g., number of processing cores, an overall processorutilization) utilized, an amount of memory utilized, an amount ofbandwidth utilized, and an amount of storage space utilized. In light ofthe present disclosure, additional or alternative execution metrics tothe discussed above may be apparent to those skilled in the art. Allsuch execution metrics are presently contemplated and considered withinthe scope of the present disclosure.

The operator service 106 may be configured to analyze configurations ofapplications executing within the computing environment 100 and togenerate corrections for the configurations. For example, as depicted,the operator service 106 may receive the execution metrics 120 and theconfiguration 108 of the application 114 and may generate aconfiguration correction 146 for the application 114. The operatorservice 106 includes a classifier model 126, which may be configured toidentify a preferred configuration 130. The preferred configuration maybe identified from among the configurations used to train the classifiermodel 126 (e.g., from among the configurations 156, 158, 160 used totest the application 114 in the testing environment 150. The preferredconfiguration 130 may be identified as a configuration that most closelyresembles the configuration 108. For example, the preferredconfiguration 130 may be identified as a configuration with similarrequired resources and/or similar performance requirements as theconfiguration 108. The preferred configuration 130 may includecorresponding expected metrics 134, which may specify one or moreexpected performance metrics for corresponding configurations. Forexample, the expected metrics 134 may specify a workload or othermeasure of expected performance capacity for the application 114 (e.g.,a number of requests processed, an amount of data transferred). Asanother example, the expected metrics 134 may specify execution targetsfor the application 114 (e.g., a maximum latency, a minimum transferspeed). In certain implementations, the classifier model 126 mayidentify more than one preferred configuration 130 and correspondingexpected metrics 134. In such instances, the expected metrics 134 mayrepresent execution targets for different implementations (e.g.,execution targets selected to optimize performance, execution targetsselected to reduce resource utilization).

In certain implementations, the operator service 106 may includedifferent classifier models 126 for one or more of the applications 114,116, 118. For example, in certain implementations, the operator service106 may have a separate classifier model 126 for each application 114,116, 118. Additionally or alternatively, the computing environment 100may have different operator services 106 with different classifiermodels 126 for different types of applications 114, 116, 118.

Based on the preferred configuration 130 identified by the classifiermodel 126, the operator service 106 may generate a configurationcorrection 146. For example, the configuration correction 146 mayinclude one or more aspects of the preferred configuration 130 (e.g.,implementation details from the preferred configuration 130). Theconfiguration correction 146 may indicate an updated configuration forthe application 114 (e.g., a complete configuration, a partialconfiguration). Additionally or alternatively, the configurationcorrection 146 may indicate particular changes that should be made tothe configuration 108 of the application 114.

The computing environment 100 may be implemented by one or morecomputing devices, such as server computers, laptop computers, personalcomputers, virtual machines, smartphones, tablets, wearable computingdevices, or any other suitable computing device. Additionally, theprocessor(s) 142 and memory 144 may be configured to implement one ormore operational features of the computing environment 100. For example,memory 144 may store instructions which when executed by one or more ofthe processor(s) 142, may cause the processor(s) 142 to execute one ormore operational features of the computing environment 100.

FIG. 1B illustrates a testing environment 150 for application validationaccording to an exemplary embodiment of the present disclosure. Thetesting environment 150 may be configured to test applications prior todeployment in computing environments 100 (e.g., cloud computingenvironments). For example, the testing environment 150 as depicted maybe testing the application 114 prior to deployment in the computingenvironment 100. The testing environment 150 may test the application114 according to testing configurations 152, which may be predefined.The testing configurations 152 include multiple configurations 156, 158,160, which may specify particular configurations for the application114. In particular, the configurations 156, 158, 160 may includeinformation similar to the configurations 108, 110, 112 discussed above.

The testing environment 150 includes testing metrics 154. The testingmetrics 154 include multiple execution metrics 162, 164, 166. Theexecution metrics 162, 164, 166 may include information regardingperformance of the application 114. For example, the execution metrics162, 164, 166 may include information regarding, e.g., response latency,computing resource utilization, and/or any of the performance measuresdiscussed above in connection with the execution metrics 120, 122, 124.The execution metrics 162, 164, 166 may also include informationregarding the operating conditions and/or workloads that the application114 operates under during testing. For example, the execution metrics162, 164, 166 may specify, e.g., a number of requests the application114 receives during testing, an amount of data for transfer during atest, an amount of available bandwidth or other system resources.

The configurations 156, 158, 160 may include configurations 156, 158,160 optimized for performance under heavy loads for the application 114and configurations 156, 158, 160 optimized for minimal resourceutilization during execution of the application 114. The application 114may be tested multiple times based on the configurations 156, 158, 160and the execution metrics 162, 164, 166. For example, each configuration156, 158, 160 may be executed according to one or more of the executionmetrics 162, 164, 166. For example, each of the execution metrics 162,164, 166 may include one or more corresponding configurations 156, 158,160 for testing. Alternatively, each of the configurations 156, 158, 160may include one or more execution metrics 162, 164, 166 for whichtesting should be performed. To test the application 114, the testingenvironment 150 may execute the application 114 according to aparticular configuration 156, 158, 160 and may record the resultingperformance in the execution metrics 162, 164, 166.

The testing configurations 152 and testing metrics 154 may be used totrain the classifier model 126 for subsequent use in the computingenvironment 100. For example, if the application 114 meets performancerequirements according to the performed tests, the application 114 maybe deployed (e.g., for production use) to computing environments such asthe computing environment 100. When deploying the application 114, thetesting environment 150 may also deploy the classifier model 126 for usein identifying preferred configurations 130. In certain implementations,the classifier model 126 may be implemented as a machine learning modelconfigured to classify received execution metrics 120 and configurations108 to identify the most similar combination of preferred configurationand expected metrics. In particular, the classifier model 126 may beimplemented as one or more of a decision tree classifier, logisticregression classifier, nearest neighbor classifier, neural networkclassifier, support vector machine, and a naïve Bayes classifier. Theclassifier model 126 may be trained based on at least a subset of thetesting configurations 152 and the testing metrics 154. For example, thetesting configurations 152 and/or testing metrics 154 may include one ormore training sets of configurations and execution metrics that may beused to train the classifier model 126. For example, the training setsmay specify a corresponding preferred configuration 130 for particularreceived configurations. For example, the configuration 156 mayrepresent an inefficient or erroneous configuration of the application114 under particular operating conditions and the configuration 158 mayrepresent a preferred configuration of the application 114 under theparticular operating conditions. The training set may therefore includethe configuration 156 and an identifier that, under the particularoperating conditions, the configuration 158 should be identified as thepreferred configuration 130 for the configuration 156. The classifiermodel 126 may analyze the training sets to predict the correspondingpreferred configuration 130. Model parameters 168 of the classifiermodel 126 may be updated based on whether the classifier model 126correctly classified the configurations within the training sets. Inparticular, the parameters may include weights (e.g., priorities) fordifferent features and combinations of features (e.g., informationincluded within the configurations and execution metrics) and updatingthe classifier model 126 may include updating one or more of thefeatures analyzed and the weights assigned to different features and/orcombinations of features. Furthermore, although discussed as aclassifier model, in other implementations, the classifier model 126 maybe implemented as other types of machine learning models (e.g.,supervised learning models, unsupervised learning models). Theclassifier model 126 may be trained until a sufficient level of accuracyin identifying the third configurations for the training sets ofconfigurations is reached (e.g., 75%, 90%, 95%). For example, thetraining process may be repeated for the same or different training setsof configurations until the sufficient level of accuracy is reached. Theclassifier model 126 may then be deployed to computing environments,such as the computing environment 100 (e.g., may be deployed incombination with the application 114).

The testing environment 150 may be implemented by one or more computingdevices, such as server computers, laptop computers, personal computers,virtual machines, smartphones, tablets, wearable computing devices, orany other suitable computing device. Additionally, the processor(s) 170and memory 172 may be configured to implement one or more operationalfeatures of the testing environment 150. For example, memory 172 maystore instructions which when executed by one or more of theprocessor(s) 170, may cause the processor(s) 170 to execute one or moreoperational features of the testing environment 150.

FIG. 2 illustrates a configuration 200 according to an exemplaryembodiment of the present disclosure. The configuration 200 may be anexemplary implementation of configurations used by the computingenvironment 100 and/or the training environment 150. For example, theconfiguration 200 may be an exemplary implementation of theconfigurations 108, 110, 112, 156, 158, 160 and/or the preferredconfiguration 130. The configuration 200 includes an application-levelconfiguration 202 and a system-level configuration 204. In certainimplementations, the configuration 200 may be implemented as a datastructure storing the application-level configuration 202 and/or thesystem-level configuration 204. For example, the configuration 200 maybe stored as one or more of an extended markup language (XML) file, aKubernetes® ConfigMap data structure, a YAML file, and/or a JavaScriptObject Notation (JSON) file.

The application-level configuration 202 may specify particular optionsand/or parameters specific to particular implementations of applications114, 116, 118 (e.g., may specify how the application 114, 116, 118executes within the computing environment 100). For example, theapplication-level configuration 202 may include implementation details206 that specify particular implementation options and/or parameters forthe applications 114, 116, 118. As a specific example, theimplementation details 206 may include a number of instances 210specifying a number of instances of the application 114, 116, 118 thatshould execute within the computing environment 100. For example,certain applications 114, 116, 118 may be capable of executing as one ormore instances executing in parallel (e.g., instances executing withinseparate containers and/or virtual machines of the computing environment100), and the number of instances 210 may specify one or more of arequired number of instances, minimum number of instances, and/ormaximum number of instances for the application 114, 116, 118. Theimplementation details 206 may also include one or moreapplication-specific parameters 212, 214. The application specificparameters 212, 214 may specify one or more parameters or options thatconfigure how the particular application 114, 116, 118 executes withinthe computing environment 100. The specific types ofapplication-specific parameters 212, 214 may differ depending on thespecific type of application. For example, for an application 114executing to provide a data grid, the application-specific parameters212, 214 may include one or more of a number of initial members expectedwhen detecting members of the data grid, a request timeout periodspecifying the maximum number of time in instance of the application 114will wait for a response when detecting members of the data grid, amember discovery protocol specifying the type of communication protocolmembers of the data grid utilized to communicate, a storageconfiguration specifying a type of formatting and/or a storage protocolused to store data within the data grid, a duplication protocolspecifying whether and how data is duplicated across multiple members ofthe data grid, and/or a maximum size of files and/or partial filesstored on the data grid. As another example, for an application 116providing data synchronization, the application-specific parameters 212,214 may specify one or more of an update frequency uploading and/ordownloading synchronized data, a maximum data size for files or partialfiles synchronized between clients, a preferred data transfer speed, adata storage format, and/or a maximum number of clients persynchronization operation. As a still further example, for anapplication 118 executing to provide a send/receive buffer, theapplication-specific parameters 212, 214 may specify one or more of anumber of buffers to be implemented by each instance of the application118, a storage capacity for each buffer, a maximum or minimum payloadsize for the buffers, and/or an uptime for instances of the application118.

Additionally or alternatively, the application-level configuration 202may identify required system resources 208 indicating amounts ofresources needed to execute the application 114, 16, 118 and/or toexecute instances of the application 114, 116, 118 within the computingenvironment 100. For example, the required system resources 208 mayspecify a required processing power 216, (e.g., a minimum number ofprocessing cores, maximum number of processing cores) and/or requiredmemory 218 (e.g., a minimum memory capacity required, a maximum memorycapacity required, a type of memory required). The required systemresources 208 may additionally or alternatively include required storage220 (e.g., a minimum amount of storage space required, a maximum amountof storage space required, a particular type of storage space required,a storage data transfer speed required) and/or a required bandwidth 222(e.g., a minimum of network bandwidth required, a maximum amount ofnetwork bandwidth required, a particular network communication interfacerequired). The required resources 208 may be specified for theapplication 114, 116, 118 overall and/or may specify the resourcesrequired for individual instances of the application 114, 116, 118.

The system-level configuration 204 may specify an amount of one or moresystem resources available for execution of applications 114, 116, 118.For example, the system-level configuration 204 may specify the amountof one or more system resources available within the computingenvironment 100 (e.g., available within the cluster in which theapplication 114, 116, 118 is executing). As a specific example, thesystem-level configuration 204 may specify one or more of availableprocessors 224 (e.g., available processing cores), available memory 226(e.g., available memory capacity and/or available memory speed),available storage 228 (e.g., available storage capacity and/or availablestorage transfer speed), and/or available bandwidth 230 (e.g., availablebandwidth transfer capacity). In certain implementations, thesystem-level configuration 204 may specify a total amount of systemresources available. Additionally or alternatively, the system-levelconfiguration 204 may specify an amount of system resources that areavailable and are not allocated for use with other system functions(e.g., other applications). For example, one or more applications mayreserve access to particular system resources (e.g., particularprocessing cores and/or particular capacities of memory), but may not becurrently using the reserve computing resources to execute. In suchinstances, the system-level configuration 204 may omit such reservedcomputing resources from indications of the available system resources.

It should be understood that certain implementations of theconfiguration 200 may differ from those depicted in FIG. 2. For example,certain implementations of the configuration 200 may lack one or more ofthe implementation details 206, the required system resources, and thesystem level configuration 204. Additionally or alternatively, certainimplementations of the required system resources 208, the implementationdetails 206, and/or the system-level configuration 204 may omit one ormore of the depicted pieces of information and/or may include additionalpieces of information. For example, the required system resources 208and/or the system-level configuration 204 may include informationregarding additional types of system resources to those depicted and/ormay exclude information regarding one or more of the depicted types ofsystem resources.

FIG. 3 illustrates an operation 300 to correct the configuration of anapplication according to an exemplary embodiment of the presentdisclosure. The operation 300 may be performed to identify a preferredconfiguration for an application and to update the configuration of theapplication based on the preferred configuration. In particular, theoperation 300 may be performed to update the configuration 306 of asend/receive buffer 302. The send/receive buffer 302 may be anapplication executing within a computing environment 100. Thesend/receive buffer 302 may be communicatively coupled to an endpoint(e.g., an endpoint of another application, such as an applicationimplementing an application programming interface (API) call). Inparticular, the send/receive buffer 302 may be configured to receive andstore data payloads intended for the application (e.g., API requests)and to transmit data payloads on behalf of the application (e.g., APIresponses).

As depicted, the configuration 306 includes an application-levelconfiguration 308 and a system-level configuration 310. Theapplication-level configuration 308 includes implementation details 312specifying that there is one instance of the send/receive buffer 302executing and that the instance is implementing two buffers (e.g., iscapable of transmitting/receiving two data payloads at the same time).For example, the number of instances and number of send/receive buffersper instance may be controlled to provide a desired number ofsend/receive buffers (e.g., sufficient send/receive buffers to receiveand process requests with a maximum amount of latency). In particular,in certain instances (e.g., where available processing cores arefragmented among different processors 142) it may be advantageous toexecute more instances of the send/receive buffer 302 spread acrossmultiple processors 142. In further instances (e.g., where manyprocessing cores are available on the same processor 142) it may beadvantageous to execute more buffers per instance of the send/receivebuffer 302 (e.g., in order to reduce container or VM-based computingoverhead for multiple instances executing in multiple containers and/orVMs).

The application-level configuration 308 also includes required systemresources 314 specifying that each buffer requires one processing coreand 0.5 Mb/s of bandwidth in order to function properly. Thesystem-level configuration 310 specifies that there are three availableprocessing cores and 3.5 Mb/s of available bandwidth within thecomputing environment 100.

The send/receive buffer 302 also includes associated execution metrics304 (e.g., execution metrics collected by the metrics service 104 duringexecution of the send/receive buffer 302 within the computingenvironment 100). The execution metrics 304 may specify operatingconditions and performance of the send/receive buffer 302. For example,as depicted, the execution metrics 304 specify that the send/receivebuffer 302 (e.g., all instances and buffers combined) receive 400requests per second and have an average request latency of 175 ms. Ingeneral, it may be preferable to process requests with latencies of 50ms or less. For example, other applications may transmit data to andreceive data from the send/receive buffer, so longer request latenciescan delay processing not only by the send/receive buffer 302, but alsoby the other applications.

Therefore, to resolve such issues, an operator service 106 may receivethe configuration 306 and the execution metrics 304 in order to correctthe configuration 306 and reduce the request latency. For example, auser implementing and/or executing the send/receive buffer 302 mayprovide the configuration 306 and the execution metrics 304 to anoperator service 106 executing within the same computing environment 100as the send/receive buffer 302. In certain implementations, theconfiguration 306 and the execution metrics 304 may be received by anoperator service 106 associated with the send/receive buffer 302 (e.g.,an operator service 106 configured to update the configurations ofapplications executing to implement send/receive buffers 302). Theoperator service 106 may analyze the configuration 306 and the executionmetrics 304 with a classifier model 126 to identify a preferredconfiguration 130. For example, the operator service 106 may include aclassifier model 126 configured to (e.g., trained to) identify preferredconfigurations 130 of send/receive buffers 302 originating from previoustesting configurations of send/receive buffers (e.g., in the testingenvironment 150).

The corresponding preferred configuration may be similar to theconfiguration 306 and/or may have corresponding reference executionmetrics similar to the execution metrics 304. The preferredconfiguration 334 may be identified as corresponding to configuration306. For example, the classifier model 126 may identify the matchedconfiguration 324 as corresponding to the configuration 306 byclassifying the configuration 306 as most closely resembling thepreferred configuration 334. In particular, the configuration 306 may beclassified based on one or more characteristics of the implementationdetails 312, the required system resources 314, and the system-levelconfiguration 310 and may additionally or alternatively be classifiedbased on the execution metrics 304. As a specific example, theclassifier model 126 may classify the configuration 306 based on therequired system resources 314. In particular, the preferredconfiguration 334 includes required system resources 340 that aresimilar to the required system resources 314. For example, the requiredsystem resources 340 specify that one processing core and 0.6 Mb/s ofbandwidth are required for each buffer that is implemented. As a furtherexample, the classifier model 126 may classify the configuration 306based on at least a portion of the execution metrics 304. For example,the expected metrics 344 indicate an expected request throughput of 390requests per second, which is similar to the request throughput of 400requests per second for the execution metrics 304. Therefore, thepreferred configuration 334 may correspond to a send/receive bufferimplementation with similar amounts of required computing resources andsimilar operational requirements. In still further examples, theclassifier model 126 may ignore certain characteristics. For example,the implementation details 338 specify that two instances of thesend/receive buffer 302 are executing and that each instances isimplementing two buffers (e.g., utilizing a total of four processingcores). Similarly, the system-level configuration 342 specifies that twoprocessing cores and 2.8 Mb/s of bandwidth are available, which differsfrom the three processing cores and 3.5 Mb/s of available bandwidthindicated by the system-level configuration 310. It should also beunderstood that the execution metrics 304, expected metrics 344,configuration 306, and preferred configuration 334 may, in certainimplementations, include additional parameters and/or items ofinformation. In such instances, the depicted parameters and/or items ofinformation may differ from the characteristics utilized to classify theconfiguration 306.

The operator service 106 may then correct the configuration 306 based onthe preferred configuration 334. For example, the operator service 106may identify a configuration correction 146 that updates all or part ofthe configuration 306 based on corresponding portions of the correctedconfiguration 334. For example, the operator service 106 may update theimplementation details 312 to be the same as the implementation details338 (e.g., to implement two instances of the send/receive buffer 302,each instance including two buffers). In certain implementations, priorto identifying and/or implementing the configuration correction 146, theoperator service 106 may compare the execution metrics 304 with theexpected metrics 344. For example, the operator service may onlyimplement a configuration correction 146 (e.g., may only update theconfiguration 306) if the execution metrics 304 differ from the expectedmetrics 344. For example, the configuration 306 may only be updated ifone or more of the metrics (or a subset of the metrics) included in theexecution metrics 304 differs from the corresponding metrics of theexpected metrics. As a specific example, the execution metrics indicatesa request latency of 175 ms, while the expected metrics 344 indicates arequest latency of 45 ms. The operator service 106 may therefore, basedon the difference, generate and apply the configuration correction 146.In certain implementations, the operator service 106 may only identify adifference if the execution metrics 304 differ by more than apredetermined amount or percentage from the expected metrics 344 (e.g.,5%, 10%, 25%). In still further implementations, the operator service106 may only identify a difference if the execution metrics 304 indicateworse performance than the expected metrics 344 (e.g., a longer latency,more computing resources utilized, a lower percentage of correctresponses).

In certain instances, the operation 300 may be performed as part ofupdating the configuration of another application. For example, thesend/receive buffer 302 may receive and transmit data payloads on behalfof another application and the configuration 306 of the send/receivebuffer 302 may be updated as a part of updating the configuration of theother application. As a specific example, the send/receive buffer 302may receive and transmit data payloads on behalf of a data grid memberand the configuration 306 may be updated in connection with updating theconfiguration of the data grid member.

It should be understood that the operation 300 as depicted merelyrepresent one embodiment of an operation to update the configuration ofthe send/receive buffer 302. For example, additional or alternativeimplementations may include configurations having more, fewer, and/ordifferent parameters and/or items of information. As another example,comparisons (e.g., comparisons performed by the classifier model 126)may consider additional or alternative characteristics of theconfiguration 306 and execution metrics 304.

FIG. 4 illustrates a method 400 for training and deploying a classifiermodel according to an exemplary embodiment of the present disclosure.The method 400 may be implemented on a computer system, such as thecomputing environment 100 and/or the testing environment 150. The method400 may also be implemented by a set of instructions stored on acomputer-readable medium that, when executed by a processor, cause theprocessor to perform the method 400. For example, all or part of themethod 400 may be implemented by the processor(s) 142, 170 and thememories 144, 172. Although the examples below are described withreference to the flowchart illustrated in FIG. 4, many other method ofperforming the acts associated with FIG. 4 may be used. For example, theorder of some of the blocks may be changed, certain blocks may becombined with other blocks, one or more of the blocks may be repeated,and some of the blocks described may be optional.

The method 400 may begin with receiving application for execution in afirst computing environment (block 402). For example, the testingenvironment 150 may receive an application 114 for execution (e.g., forexecution of a send/receive buffer and/or a data grid). In particular,the testing environment 150 may receive the application 114 for testingand validation prior to deployment in a second computing environment,such as the computing environment 100.

The application may be executed a plurality of times according to aplurality of configurations (block 404). For example, the testingenvironment 150 may execute the application 114 multiple times accordingto multiple configurations 156, 158, 160. As described above, theapplication 114 may be executed often times for different combinationsof configurations 156, 158, 160 and execution metrics 162, 164, 166specifying operating conditions for the application 114 (e.g., differentpredetermined tests specifying particular combinations). As a specificexample, the application 114 may execute to provide a send/receivebuffer 302. The configurations 156, 158, 160 may specify, e.g.,different numbers of instances, different buffers. Instance, differentamounts of processors and/or bandwidth per buffer. Similarly, theexecution metrics 162, 164, 166 may specify different amounts ofrequests received per second and/or different amounts of datatransmitted with each transmitted response.

A plurality of execution metrics may be measured associated with theplurality of configurations (block 406). For example, the testingenvironment 150 may measure a plurality of execution metrics 162, 164,166 associated with the different configurations 156, 158, 160.Continuing the previous example, where the application 114 executes toprovide a data buffer, the testing environment 150 may execute theapplication 114 according to the configurations 156, 158, 160 (e.g.,with different numbers of instances and/or buffers) and may measure theresulting request latency. As discussed above, the execution metrics162, 164, 166 may specify operating conditions for the application 114,and different configurations 156, 158, 160 may be executed for each ofthe specified operating conditions (e.g., according to one or morepredetermined tests). The resulting execution metrics (e.g., performancemetrics) may be stored with identification of the correspondingconfiguration for each configuration 156, 158, 160 executed according tothe execution metrics 162, 164, 166.

A classifier model may be trained to identify one or more preferredconfigurations of the application (block 408). For example, the testingenvironment 150 may train the classifier model to identify one or morepreferred configurations 130 of the application 114. To train theclassifier model 126, one or more parameters 168 of the classifier model126 may be updated. For example, the model parameters 168 may identifywhich features of received configurations and execution metrics are usedto identify corresponding preferred configurations 130. Updating themodel parameters 168 as a result of the training may add or removecharacteristics of configurations and execution metrics considered whenidentifying preferred configurations 130. Additionally or alternatively,updating the model parameters may change (e.g., increase or decrease)weights associated with particular characteristics.

The classifier model may be provided to a second computing environment(block 410). For example, the classifier model 126 may be provided to asecond computing environment 100 used to execute applications 114, 116,118 in a production setting. In particular, the classifier model 126 maybe received from the testing environment 150 along with the application114, e.g., after the application 114 passes the performed tests and/orafter the classifier model 126 is trained to a sufficient level ofaccuracy. In certain implementations, the testing environment 150 may bepart of the same computing infrastructure (e.g., a cloud computinginfrastructure) is the computing environment 100. The testingenvironment 150 may accordingly transmit the classifier model 126 and/orthe application 114 to the computing environment 100 via a networkconnection (e.g., an Internet network connection, a local networkconnection within the cloud computing infrastructure). Additionally oralternatively, the testing environment 150 may be implemented as part ofthe computing environment 100. In such instances, the testingenvironment 150 may provide the classifier model 126 and/or theapplication 114 to the computing environment 100 by making theclassifier model 126 and/or the application 114 accessible to thecomputing environment 100 (e.g., a runtime environment and/or anoperator service of the computing environment 100).

Inefficient configurations for subsequent deployments of the applicationwithin the second computing environment may be detected using theclassifier model (block 412). For example, the classifier model 126 maydetect inefficient configurations for subsequent deployments (e.g.,instances) of the application 114 within the computing environment 100.In particular, the computing environment 100 may execute the application114 according to a particular, specified configuration 108 (e.g., aconfiguration 108 received from an entity in whose behalf theapplication 114 is executed). While executing the application 114, ametrics service 104 may collect execution metrics 120 regarding theexecution of the application 114. The classifier model 126 may receivethe configuration 108 in the execution metrics 120 in order to analyzethe configuration 108 in the execution metrics 120 to determine whetherthe configuration 108 is inefficient and/or undesirable (e.g., utilizesexcessive computing resources, fails to meet one more performancerequirements). To detect inefficient configurations of the application114, the classifier model 126 may identify preferred configurations 130and/or expected metrics 134 and may compare the expected metrics 134 tothe execution metrics 120. In particular, the classifier model 126 mayidentify inefficient configurations without transferring informationfrom the second computing environment, which may improve privacyconfidentiality protections, as explained further below.

Performing the method 400 may enable the testing environment 150 totrain and configure the classifier model 126 to identify inefficientconfigurations of applications executing within other computingenvironments 100. In particular, the classifier model 126 may beclassify configurations as inefficient that differ from preferredconfigurations 130. Further, by detecting such inefficientconfigurations, the method 400 may enable improved performance forapplications that are executing within the computing environments 100(e.g., may improve responsiveness, execution speed, and/or may reduceoverall resource utilization, freeing up additional resources for use inexecuting other applications). Further, the method 400 enables theclassifier model 126 to be trained using existing testing systems andexamples. By utilizing existing testing examples, the classifier model126 can be trained without requiring the creation of specializedtraining datasets. Further, by utilizing existing testing systems, theclassifier model 126 may be trained as part of testing and deploying theapplication 114, which may reduce the amount of time required to trainthe classifier model, resulting in faster deployment of both theapplication 114 and the classifier model 126.

FIG. 5 illustrates a method 500 for validating, deploying, andcorrecting the configuration of applications according to an exemplaryembodiment of the present disclosure. The method 500 may be implementedon a computer system, such as the computing environment 100 and/or thetesting environment 150. In particular, the method 500 includes atesting environment 522, which may be an exemplary implementation of thetesting environment 150, a computing environment 524, which may be anexemplary implementation of the computing environment 100, and anoperator service 526, which may be an exemplary implementation of theoperator service 106. The method 500 may also be implemented by a set ofinstructions stored on a computer-readable medium that, when executed bya processor, cause the processor to perform the method 500. For example,all or part of the method 500 may be implemented by the processor(s)142, 170 and the memories 144, 172. Although the examples below aredescribed with reference to the flowchart illustrated in FIG. 5, manyother method of performing the acts associated with FIG. 5 may be used.For example, the order of some of the blocks may be changed, certainblocks may be combined with other blocks, one or more of the blocks maybe repeated, and some of the blocks described may be optional.

The method 500 may begin with receiving an application (block 530). Forexample the testing environment 522 may receive an application 114 fortesting and validation prior to deployment. The application may beexecuted a number of times according to a plurality of configurationsand execution metrics may be measured (block 532). For example, thetesting environment 522 may execute the application 114 multiple timesaccording to multiple configurations 156, 158, 160 and may measureexecution metrics 162, 164, 166 based on the executions of theapplication 114, as described above. The classifier model may be trained(block 534) and the application may be deployed (block 536). Forexample, the classifier model 126 may be trained to identify preferredconfigurations for implementations of the application 114 and theapplication 114 may be deployed by providing the application to thecomputing environment 524, as described above.

The application may be received along with a configuration for theapplication (block 538). For example, the computing environment 524 mayreceive the application 114 for the testing environment 150 may receivea configuration 108 for the application 114 (e.g., at an API service102) along with a request to execute the application (e.g., a requestreceived from a user and/or another computing process). The applicationmay be executed and execution metrics may be measured (block 540). Forexample, the computing environment 524 may execute the application 114according to the received configuration 108 and may measure executionmetrics 120 concerning the operation of the application 114 according tothe configuration 108. For example, the execution metrics 120 maymeasure operating conditions for the application 114 (e.g., informationconcerning a work load of the application 114) and/or may measureperformance metrics of the application 114 (e.g., information concerningperformance of the application 114 under the workload).

The classifier model may then be received (block 542). For example, theoperator service 526 may receive the classifier model 126 from thetesting environment 522 after training of the classifier model 126 iscomplete. The configuration and execution metrics may also be received(block 544). For example, after executing the application at block 540,the computing environment 524 may transmit the configuration 108 andexecution metrics 122 the operator service 526. In certainimplementations, the operator service 526 may be configured to have nofurther connectivity with the testing environment 522. For example, theoperator service 526 may be configured to only receive the classifiermodel 126 from the testing environment and to receive no further updatesor information. Such implementations may improve security, e.g., bypreventing alterations to the classifier model 126 and/or by prevent theexecution metrics and other information analyzed by the classifier model126 from being accessed by other processes or environments.

A preferred configuration and expected metrics may be identified (block546). For example, the operator 526 may identify a preferredconfiguration 130 and expected metrics 134 corresponding to theconfiguration 108 and/or the execution metrics 120. The preferredconfiguration and/or expected metrics 134 may be identified by a machinelearning model, such as the classifier model 126. For example, theclassifier model 126 may be trained to classify the configuration 108and the execution metrics 120 into on one or more categories defined byone or more of the testing configurations 152 (e.g., defined duringtraining of the classifier model 126 based on the testing configurations152) and to identify the category including most similar combination ofconfiguration and expected metrics. In particular, the classifier model126 may identify the preferred configuration 130 which, in combinationwith corresponding reference execution metrics 134, most closelyresembles the execution metrics 120 and the configuration 108. In anexample where the application 114 is executing to provide responses toAPI calls, the configuration 108 may specify system requirements forinstances of the application 114 executing within the computingenvironment 100 and the execution metrics 120 may specify, e.g., anumber of requests received by the application 114. The preferredconfiguration 130 identified by the classifier model 126 may includesimilar system requirements for instances of the application 114 and theassociated expected metrics 134 may include similar numbers of requests.

A difference may be identified between the execution metrics and theexpected metrics (block 548). For example, the operator service 526 mayidentify a difference between the execution metrics 120 and the expectedmetrics 134. As claimed above, the difference may be identified bycomparing particular portions of the execution metrics 120 and theexpected metrics 134, such as portions indicating applicationperformance (e.g., response latencies and/or resource utilization). Incertain implementations, to identify a difference, the operator service526 may have to determine that the difference between correspondingmetrics of the execution metrics 120 and the expected metrics 134 exceeda certain predetermined threshold (e.g., a percentage-based threshold oran absolute threshold).

The preferred configuration may then be applied (block 550). Forexample, the computing environment 524 may apply the preferredconfiguration 132 all or part of the configuration 108 of theapplication 114. In applying the preferred configuration 130, thecomputing environment 524 may generate a configuration correction 146that changes all or part of the configuration 108. In certainimplementations, the configuration correction 146 may be generated basedon a portion of the preferred configuration 130 (e.g., a differencebetween a portion of the preferred configuration 130 and a correspondingportion of the configuration 108). As a specific example, theconfiguration correction may be generated by identifying differencesbetween the implementation details of the preferred configuration 130and the configuration 108 and generating the configuration correction146 to remove and/or reduce the differences. For example, theconfiguration 108 may indicate that a single instance of the application114 is executing to service API requests and that the single instance ofthe application 114 is allocated 1 Mb/s of bandwidth. The executionmetrics 120 may indicate that the application 114 is servicing 100requests per second and has a response latency of 75 ms. The preferredconfiguration 130 may indicate that the application has three instancesthat are executing and that each instance has 0.7 Mb/s of bandwidthallocated (for a total of 2.1 Mb/s of bandwidth for the application). Incertain implementations, the preferred configuration 130 may alsoinclude associated expected metrics 134 indicating improved performance(e.g., 90 requests per second received at a response latency of 10 ms).Based on the preferred configuration 130 the configuration correction146 may be identified to include increasing the number of instances ofthe application 114. Additionally or alternatively, the computingenvironment 524 may update all or part of the configuration 108 (e.g.,implementation details) to be the same as the corresponding portions ofthe preferred configuration 130.

By performing the method 500, the computing environment 100 may be ableto improve the performance of applications that are executing withinefficient or erroneous configurations. In particular, whereapplications are executing below an expected performance threshold, theconfigurations of the applications may be analyzed by the operatorservice 526 according to the method 500 in order to restore properperformance of the applications. Additionally, the classifications andcorrections made by the operator service 106 may be customized fordifferent deployments. For example, in certain implementations, separateclassifier models may be trained for different deployment contexts(e.g., based on tests performed prior to deploying applications).Further, the operator service 526 and the classifier model 126 may becapable of executing entirely within the computing environment 524 andwithout transferring data (e.g., data regarding the configuration 108,the application 114, and/or the execution metrics 120) outside of thecomputing environment 524 (e.g., a cluster executing the application114). Such contained analysis may protect the confidentiality ofsensitive applications and/or information and may assist in complyingwith privacy regulations, such as the European General Data ProtectionRegulation (GDPR).

FIG. 6 illustrates a system 600 according to an exemplary embodiment ofthe present disclosure. The system 600 includes a first computingenvironment 602 and a second computing environment 604. The firstcomputing environment 602 includes a first processor 606 and a firstmemory 608. The first memory 608 stores instructions 610 which, whenexecuted by the first processor 606, cause the first processor 606 toreceive an application 612 for execution in a first computingenvironment 602 and execute the application 612 a plurality of times614, 616 according to a plurality of configurations 618, 620,respectively. The instructions 610 may further cause the first processor606 to measure a plurality of execution metrics 622, 624 associated withthe plurality of configurations 618, 620. A classifier model 626 may betrained, based on the plurality of execution metrics 622, 624 and theplurality of configurations 618, 620, to identify one or more preferredconfigurations 628 for the application 612. The classifier model 626 maythen be provided to the second computing environment 604. The secondcomputing environment 604 may include a second processor 630 and asecond memory 632. The second memory 632 may store instructions 634which, when executed by the second processor 630, cause the secondprocessor 630 to detect, using the classifier model 626, inefficientconfigurations 636 for subsequent deployments of the application 612within the second computing environment 604 without transmittingconfigurations 636 or the application 612 from the second computingenvironment 604.

All of the disclosed methods and procedures described in this disclosurecan be implemented using one or more computer programs or components.These components may be provided as a series of computer instructions onany conventional computer readable medium or machine readable medium,including volatile and non-volatile memory, such as RAM, ROM, flashmemory, magnetic or optical disks, optical memory, or other storagemedia. The instructions may be provided as software or firmware, and maybe implemented in whole or in part in hardware components such as ASICs,FPGAs, DSPs, or any other similar devices. The instructions may beconfigured to be executed by one or more processors, which whenexecuting the series of computer instructions, performs or facilitatesthe performance of all or part of the disclosed methods and procedures.

It should be understood that various changes and modifications to theexamples described here will be apparent to those skilled in the art.Such changes and modifications can be made without departing from thespirit and scope of the present subject matter and without diminishingits intended advantages. It is therefore intended that such changes andmodifications be covered by the appended claims.

1. A method comprising: receiving an application for execution in afirst computing environment; executing the application a plurality oftimes according to a plurality of configurations; measuring a pluralityof execution metrics associated with the plurality of configurations;training, based on the plurality of execution metrics and the pluralityof configurations, a classifier model to identify one or more preferredconfigurations for the application; providing the classifier model to asecond computing environment; and detecting, using the classifier model,inefficient configurations for subsequent deployments of the applicationwithin the second computing environment.
 2. The method of claim 1,wherein the first computing environment is a testing environmentconfigured to validate applications prior to deployment.
 3. The methodof claim 2, wherein executing the application the plurality of timesincludes executing a plurality of predetermined tests prior todeployment of the application, and wherein measuring the plurality ofexecution metrics includes measuring the execution metrics during thepredetermined tests.
 4. The method of claim 2, wherein the testingenvironment is associated with a first entity, and wherein the secondcomputing environment is configured to execute applications on behalf ofa second entity.
 5. The method of claim 1, wherein detecting inefficientconfigurations for subsequent deployments of the application furthercomprises: receiving (i) a configuration for the application within thesecond computing environment and (ii) execution metrics of theapplication within the second computing environment; identifying, withthe classifier model, a corresponding preferred configuration andexpected metrics associated with the corresponding preferredconfiguration; identifying a difference between at least one of theexecution metrics and at least one of the expected metrics; and applyingthe corresponding preferred configuration to the application within thesecond computing environment.
 6. The method of claim 5, wherein theconfiguration and at least a subset of the plurality of configurationsinclude an application-level configuration specifying at least one of(i) application-specific implementation details and (ii) systemresources required for execution.
 7. The method of claim 6, wherein theconfiguration and the subset of the plurality of configurations furtherinclude a system-level configuration specifying an amount of one or moresystem resources available for execution of the function.
 8. The methodof claim 7, wherein identifying the preferred configuration includescomparing both the application-level configuration and the system-levelconfiguration to the subset of the plurality of configurations.
 9. Themethod of claim 5, wherein the configuration is received from anapplication programming interface service of the second computingenvironment, the application programming interface being configured togenerate and apply configurations to applications executing within thesecond computing environment.
 10. The method of claim 1, wherein theplurality of configurations include configurations optimized forperformance under heavy loads and configurations optimized for minimalresource utilization during execution of the application.
 11. The methodof claim 1, wherein the execution metrics include at least one of alatency of the application, a throughput of the application, a processorutilization of the application, a memory utilization of the application,and a storage utilization of the application.
 12. A system comprising afirst computing environment and a second computing environment, thefirst computing environment comprising: a first processor; and a firstmemory storing instructions which, when executed by the first processor,cause the first processor to: receive an application for execution inthe first computing environment; execute the application a plurality oftimes according to a plurality of configurations; measure a plurality ofexecution metrics associated with the plurality of configurations;train, based on the plurality of execution metrics and the plurality ofconfigurations, a classifier model to identify one or more preferredconfigurations for the application; and provide the classifier model tothe second computing environment, the second computing environmentcomprising: a second processor; and a second memory storing instructionswhich, when executed by the second processor, cause the second processorto: detect, using the classifier model, inefficient configurations forsubsequent deployments of the application within the second computingenvironment.
 13. The system of claim 12, wherein the first computingenvironment is a testing environment configured to validate applicationsprior to deployment.
 14. The system of claim 13, wherein executing theapplication the plurality of times includes executing a plurality ofpredetermined tests prior to deployment of the application, and whereinmeasuring the plurality of execution metrics includes measuring theexecution metrics during the predetermined tests.
 15. The system ofclaim 13, wherein the testing environment is associated with a firstentity, and wherein the second computing environment is configured toexecute applications on behalf of a second entity.
 16. The system ofclaim 12, wherein the second memory stores further instructions which,when executed by the second processor while detecting inefficientconfigurations for subsequent deployments of the application, cause thesecond processor to: receive (i) a configuration for the applicationwithin the second computing environment and (ii) execution metrics ofthe application within the second computing environment; identify, withthe classifier model, a corresponding preferred configuration andexpected metrics associated with the corresponding preferredconfiguration; identify a difference between at least one of theexecution metrics and at least one of the expected metrics; and applythe corresponding preferred configuration to the application within thesecond computing environment.
 17. The system of claim 16, wherein theconfiguration and at least a subset of the plurality of configurationsinclude an application-level configuration specifying at least one of(i) application-specific implementation details and (ii) systemresources required for execution.
 18. The system of claim 17, whereinthe configuration and the subset of the plurality of configurationsfurther include a system-level configuration specifying an amount of oneor more system resources available for execution of the function. 19.The system of claim 18, wherein identifying the preferred configurationincludes comparing both the application-level configuration and thesystem-level configuration to the subset of the plurality ofconfigurations.
 20. A non-transitory, computer-readable medium storinginstructions which, when executed by at least one processor, cause theat least one processor to: receive an application for execution in afirst computing environment; execute the application a plurality oftimes according to a plurality of configurations; measure a plurality ofexecution metrics associated with the plurality of configurations;train, based on the plurality of execution metrics and the plurality ofconfigurations, a classifier model to identify one or more preferredconfigurations for the application; provide the classifier model to asecond computing environment; and detect, using the classifier model,inefficient configurations for subsequent deployments of the applicationwithin the second computing environment.